home *** CD-ROM | disk | FTP | other *** search
- Path: comma.rhein.de!serpens!not-for-mail
- From: mlelstv@serpens.rhein.de (Michael van Elst)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Replying to WB Startup message with Sas/C
- Date: 17 Feb 1996 20:16:07 +0100
- Organization: dis-
- Message-ID: <4g59hn$m1v@serpens.rhein.de>
- References: <717.6614T755T957@codeworks.gen.nz> <388.6614T873T1805@nando.net> <DMtLxL.7oo@unx.sas.com> <8Wt6y*QWf@yaps.rhein.de>
- NNTP-Posting-Host: serpens.rhein.de
-
- arno@yaps.rhein.de (Arno Eigenwillig) writes:
-
- >In article <DMtLxL.7oo@unx.sas.com>, James Cooper writes:
-
- >> myproc = (struct Process *)FindTask(NULL);
- >> if (myproc->pr_CLI == NULL)
- >> myWBS = (struct WBStartup *)GetMsg(myproc->pr_MsgPort);
-
- >Huh? Shouldn't you WaitPort() somewhere?
-
- You should. _Currently_ it doesn't matter because Workbench creates
- a Task at priority 0 and runs at priority 1. So your process won't
- be scheduled before the startup message is sent to you. But that's
- just chance. To be safe you must wait for the message.
-
- Regards,
- --
- Michael van Elst
-
- Internet: mlelstv@serpens.rhein.de
- "A potential Snark may lurk in every tree."
-